iLoADER |
HOME |
Handling data load errorsErrors that occur during data loads are written to the iLoader log file. A separate log file is created for each data load. iLoader will endeavor to continue running beyond errors that occur, unless they are terminal and no additional processing can take place. Other progress messages are also placed in the log file, so that it is possible to see at which point the load error occurred. If a file is missing when the Control Script begins processing, the system will log an error and proceed. The system will not wait indefinitely for the file to arrive, if it does not open the named file successfully, it will log an error and proceed. It is assumed all data files are present within the specified directory before the Control Script is copied. If a file is corrupt or incomplete when processing begins it will attempt to load the file. When it reaches the corrupt area of the file it will log an error and stop. At this point, the table into which the data was being loaded will be in an inconsistent state and should not be used. The same applies if the fields have been defined incorrectly. If this is the case, the database itself will no longer contain valid information and should be restored from back up prior to use. iLoader can be configured to automatically run the back up if a script fails. This is done by adding a Rollback command (ENABLE_ROLLBACK=TRUE) to the Control File. |
Online & Instructor-Led Courses | Training Videos | Webinar Recordings | ![]() |
|
![]() |
© Alterian. All Rights Reserved. | Privacy Policy | Legal Notice | ![]() ![]() ![]() |